this is expected to fail on the first go - making sure it catches this failure

When we run code generation, new versions of the aws golang v2 sdk are automatically fetched, and used in codegen for go generate ./pkg/awsapi/...

Won't this make it so that, if any of the aws services we use in that package are updated, this will just start failing the test-and-build check until someone updates and merges a fix, and everyone else rebases? Either that, or every PR is going to have to include autogen updates from AWS service updates in each of their PRs, and keep them up to date as AWS keeps their service up to date, making stale PRs more difficult to deal with?

I'm not convinced this is the right approach here.

Maybe we should either change the make build target to not run the auto-gen, or isolate the part about dynamically fetching new versions of the aws sdk for auto-gen to its own gen target that's not run by default or something? Then I would be more OK with checking for auto-gen diff like this if it doesn't rely on dynamically updating external dependencies.